fix(arborist): re-apply packageExtensions to the linked actual tree#9569
Merged
owlstronaut merged 1 commit intoJun 18, 2026
Merged
Conversation
manzoorwanijk
force-pushed
the
fix/linked-packageextensions-actual-tree
branch
from
2e0f44d to
71de540
Compare
owlstronaut
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up of #9496
Under
install-strategy=linked, a rootpackageExtensionsrule that adds a missing dependency installs and works at runtime, but every command that reads the actual tree loses the edge:npm ls --all --jsonomits the extension-created dependency and its provenance.npm explain <dep>fails withNo dependencies found matching <dep>.npm patch add <dep>fails withEPATCHNOTINSTALLED.Hoisted installs and normally-declared transitive deps are unaffected.
References
Fixes #9568